Loading...
 
Skip to main content

Tracker Events

Events on Tracker items: Changing status & email notification in advanced
It is possible to specify automatic item status change for a tracker after a certain period of inactivity. Moreover, some emails can be sent to warn the user about that change at some predefined time before the status item change is planned to happen.

You can define it through the "Events" option for tracker; the icon is shown in the list of Trackers (tiki-list_trackers.php) > column "Actions": Image

Click to expand
Click to expand


The interface for the status change based on the batch job looks something like (depending on your Tiki version):


The status change is done before considering to send notification.
The time the event is approximate as it depends of the frequency of the cron

The task that must be run is

cron command
Copy to clipboard
cd /path_to_tiki_root; php tiki-batch_todo.php


In the modification/creation panel of a tracker, you can specify a change of status from one status (optional) to another after a certain time from the creation or last modification of an item. You can also specify if you wish to send a notification to the item creator. The subject of the message is a string. The body of the message is a smarty resource, either a wiki page or a template, which can use a few variables inside:

  • {$todo_itemId}
  • {$todo_tostatus}
  • {$todo_fromstatus}
  • {$todo_after}
  • {$todo_desc} , which is fed with the first "isMain" type of field from that tracker, which could be the "title" or "name" assigned to that tracker item at item creation, etc.



Example ( in Tiki6 ):

batch1.gif
wiki page changeStatus
Copy to clipboard
In about {$todo_after|duration}, the item {$todo_itemId} ("{$todo_desc}") will change from the status {$todo_fromstatus} to {$todo_tostatus}

In this example open items older than one day will have their status changed to pending. The item creator will receive a notification 23 hours before the change.

Since Tiki9, the events on tracker items can be run by means of Token Access.

Related:


Alias names for this page:
TrackerEvents | TrackerEvent | Tracker Event